Komputer for Alle 2001 #6

home *** CD-ROM | disk | FTP | other *** search

/ Komputer for Alle 2001 #6 / CD 6 (Black) - 2001.iso / Tools / MBProbe / Faq.txt next >

Wrap

Text File | 1999-10-27 | 14.8 KB | 280 lines

MBProbe Frequently Asked Questions Copyright 1998-99 Jonathan Teh Soon Yew http://web.bham.ac.uk/jst829/mbprobe/ General ------- Q: Does MBProbe slow down my computer? A: Yes, by a little. ANY program running in the background will slow down the computer. The question is: by how much? MBProbe only polls the monitoring chips once every 5 seconds and does some trivial calculations and comparisons so the impact on system performance is negligible. You certainly won't notice it and it probably won't affect benchmarks like Winbench or Winstone either. Q: It says "Unable to open giveio.sys driver" in Windows NT/2000 and quits. I thought you said it supported Windows NT/2000. A: It does. You must install the giveio.sys driver first using NTINST otherwise MBProbe will be unable to access I/O ports. Refer to readme.txt. Q: Why does it detect my Celeron/Xeon as a Pentium II .25u? A: That's what it is. Essentially, all 3 CPUs share the Deschutes core which is a Pentium II core on a .25 micron process. The difference lies in the amount of L2 cache- Celeron has 0K, Pentium II has 512K running at half core speed and a Pentium II Xeon has up to 2MB running at core speed. Q: Why does it detect my Celeron A as a Pentium II A? A: That's just my own naming ;) Essentially, it is a Pentium II core on a .25 micron process with the L2 cache on the same die as the CPU. Q: Why does my system hang/reboot when MBProbe tries to suspend it? A: This is a power management issue rather than an MBProbe issue as it is calling a proper, documented Win32 API function to suspend the system. Your system doesn't have power management setup properly or one of the drivers in your system does not support power management correctly and needs to be upgraded. You can opt for MBProbe to do nothing or to shutdown the system instead. Q: How do I change the directory where the logs are generated? A: Simply start MBProbe from a different directory. Edit the properties of the MBProbe shortcut and change the path in the 'Start in' entry. Q: Why does Scandisk or Defrag keep restarting? A: The logging options write something to the hard drive occassionally, especially history logging. Disable logging for the duration of the Scandisk or Defrag. Q: How do I specify arguments for the executable run by a warning event? A: You can't. Write a script for this either using JScript or VBScript. You need to have the Windows Scripting Host for this to work. Other scripting languages like Perl will also work as long as you associate the .perl file type with the Perl interpreter executable. In fact, any file type with an 'Open' function defined will work. Q: How do get it to do ... when a warning event occurs? A: Write a script to do it and put that as an executable. With the right scripting language (and some programming skills) you can get it to do practically anything :) Hardware -------- Q: How do I know whether my motherboard has a monitoring chip? A: The easiest way is to just run MBProbe and see if it finds anything. Some recent motherboards do include a hardware monitoring chip. The following indicates your motherboard has a monitoring chip: 1. The BIOS setup has voltage/temperature/fan speed readings. 2. The motherboard comes bundled with some monitoring software or Intel LANDesk Client Manager with temperature monitoring. 3. You check the motherboard and find one on it :) These may indicate that your motherboard does not have a monitoring chip: 1. You have a branded computer or have an OEM motherboard. Some motherboard manufacturers like Asus, Intel and QDI do not include hardware monitoring in their OEM boards. Q: I'm very sure my motherboard has a hardware monitoring chip but it still says "None". A: So it does. Check the list of unsupported chips first to see if the chip in your motherboard is listed there. If it is, you're out of luck. If not, it may be that your chip isn't where MBProbe expects it to be. The LM78-type chips are searched for at ISA port 290h. Other hardware monitoring chips are searched for at SMBus address 28h-2fh. Chips at other ports/addresses will not be found. If you have such a configuration, try to find out the address of the chip and contact me with the information. SMBus monitoring chips are slave devices and as such need a supported SMBus host. Q: My SMBus host shows "(Disabled)". How do I enable it? A: Some chipsets (e.g. ALi) have the SMBus host and power management controller as one device. Try enabling power management in the BIOS setup. For other chipsets, a BIOS upgrade may be necessary. Contact your vendor. Q: My motherboard has a VIA MVP3 chipset. Why isn't the SMBus being detected? A: Most MVP3 chipsets actually come with a VT82C586B south bridge which has an I2C host and not an SMBus host. This is unsupported (read the manual for the reason). Q: What's SMBus? A: SMBus is Intel's System Management bus which is subset of the Philips I2C bus. It is a two-wire serial interface for devices such as hardware monitors, smart batteries and power management related chips. Devices on the bus are SMBus slaves and thus requires an SMBus host to communicate with them. For further information refer to techinfo.txt for the location of the SMBus specification sheet. Voltage ------- Q: The voltage readings are screwed. What's wrong? A: This is due to some motherboard manufacturers connecting different voltages to the monitoring chips. Refer to the known issues section in the readme. Please report your complete set of readings (from MBProbe and another source such as the BIOS, in the original order), motherboard model and I will try and correct it. For the time being, disable the warnings. There is an option to use an alternate voltage order for SiS5595 chips. Try it and see if it corrects the readings. Q: Why are there two Vccp readings? A: That's what the monitoring chip supports. Dual processor boards have one reading for each processor. On my (uniprocessor) Asus P2B, they're both the same. The Tekram P6B40-A4X connects the Vccp2 input to a thermistor instead and as such gives a nonsensical Vccp2 reading. Disable the warning for it. Q: Why does the Vccp2/+2.5V reading show 1.5V? A: Some boards (Intel, QDI) have Vccp2 or +2.5V connected to Vtt instead which has a nominal voltage of +1.5V. Adjust the nominal voltage in the voltage tab accordingly. Vtt is the AGTL+ bus termination voltage. Q: Why are some of the voltage readings/adjustments disabled? A: Some monitoring chips do not support certain readings. E.g. LM78-type chips are normally not setup to monitor +2.5V. Q: Why are the +12V, -5V and -12V readings slightly off? A: Please switch the voltage divider mode in the properties dialog. This option is only enabled for LM78/79 and SiS5595. Reason: Voltages are 'divided' with resistors before connection to the chip. Most motherboard manufacturers actually use resistor values meant for the Winbond W83781D even though they have installed an LM78/79. Some motherboard manufacturers do use the proper resistor values (e.g. Tekram) hence the need for the new switch as there is no way of determining the values via software. The default is the Winbond values; if these give readings which are too low, switch to the LM78 values. Q: Why can't I enable warnings for both Vccp2 and -12V? A: You have a Heceta 2/3 monitoring chip. The Vccp2 and -12V readings are read from the same location hence only one of the readings would make sense. This depends on what the motherboard manufacturer actually connected to that input. Intel boards have it connected it to -12V. Q: The monitoring software that came with my GL518SM shows 4 voltages but only the Vccp1 reading in MBProbe is correct. A: The GL518SM can monitor 4 voltages but can only show the value for 1, in this case it's Vin3 on chip which generally is connected as Vccp1. The other voltages can only be monitored for exceeding the limits but their current values cannot be read. The monitoring software you have is 'reading' the value by continuously resetting the limits and checking whether the voltage exceeds that limit. This is not implemented in MBProbe and probably will never be. Q: It displays my CPU voltage as 0.00V. What's wrong? A: Chances are your CPU is either too old or too new. In particular, CPU voltages for 486 and early Pentium 60/66 CPUs are not in the program since it is assumed that motherboards supporting CPUs that old would not be equipped with a hardware monitoring chip. The other case is that the CPU is too new and MBProbe has not been updated yet to take this into account. Please e-mail me with full details of your processor (manufacturer, model, clock, voltage) and I will update MBProbe. Q: It detects my CPU voltage incorrectly. What effect does this have? A: This is harmless; simply select the correct CPU core voltage in the 'Voltage' tab. MBProbe guesses the CPU voltage via its CPUID. This is basically the information you see under 'CPU information' on the 'General' tab in Properties. The problem with this is that the CPUID doesn't always differentiate every single variant of a particular CPU. You can either guess the voltage of your CPU based on the value returned by the monitoring chip, check the table in techinfo.txt or look for it on the CPU itself. Temperature ----------- Q: Why is the default temperature display in Fahrenheit? A: It is the default only if your regional settings (in the Control Panel) is set to English (United States). Many people forget to change the regional settings when installing Windows. Just change the temperature display to Celsius if you like. Q: Can my board monitor CPU temperature? A: I don't know. If MBProbe assigns a sensor to the CPU temperature, then it probably can. You may have to change some settings and/or plug in a thermistor into the motherboard and attach it to the CPU. Note that most LM78/79 and Heceta2 equipped boards cannot monitor CPU temperature. Refer to techinfo.txt for board-specific details. Q: What type of thermistor should I use? A: If you have a Winbond chip it's an NTC type, 10Kohm @ 25C, B-value 3435. Visit your local electronics hobbyist store for the thermistors or ask the dealer where you purchased your motherboard from. Q: Why do the temperature readings show -48C? A: You probably have a Winbond chip. The two -48C readings are coming from external temperature inputs which are unconnected. You need to get two thermistors and connect them to the corresponding pins on the motherboard. On my Asus P2B, they are labeled Q: Why do I get the same readings from the LM75:1, 0 and W8378xx:2, 3? A: The Winbond chips simulate two LM75s (W83783S simulates 1 only) and as such gives identical readings to its own 2nd and 3rd temperature inputs. Usually W8378xx:2 is equivalent to LM75:1 and W8378xx:3 to LM75:0. Q: What's the difference between using MAX1617:x and MAX1617:xR? A: Refer to techinfo.txt under MAX1617. Q: Why is the 'CPU thermal diode' section greyed out? A: They are only enabled for certain chips. Winbond W83782D and W83783S chips accept either a thermal diode or thermistor on their temperature inputs. Enable the appropriate box to ensure a correct reading of the CPU temperature. Abit boards have the thermal diode connected to Sensor:2. ADM1024 chips can have 2 of the pins configured to accept either a thermal diode or two voltage readings (2.5V and Vccp2). When the Sensor:3 option is enabled the 2.5V, Vccp2 and -12V readings will be unavailable. Q: How did the LM78/79 gain an extra temperature input? A: The Tekram P6B40-A4X uses the Vccp2 input for a thermistor instead and this is LM78:2 under MBProbe. Of course, on other boards this will give you a nonsensical value as Vccp2 is usually connected to the CPU core voltage or to Vtt (1.5V). Do NOT try to reconnect it to a thermistor in a vain attempt to get a temperature reading! Q: Why is a CPU temperature offset needed? A: This is normally needed on motherboards using a temperature sensor under a socketed CPU. The sensor is not in direct contact with the CPU, hence the requirement for an offset to account for the insulating layer of air between the sensor and the CPU. Q: What's a FanTemp? A: FanTemp is a temperature sensor for use in systems with motherboards which are equipped with a hardware monitoring chip that does not support external temperature inputs. It contains a thermistor that can be attached to the CPU or other device of interest and a microcontroller- based circuit that measures the temperature and interfaces to the hardware monitor through an unused fan connector on the motherboard. This also means that you will lose that fan connection. MBProbe will disable a fan input which has been assigned as a FanTemp temperature sensor. For further information, please contact the designer of FanTemp: Bruce Fishbein <bjfishbein@excite.com> Fans ---- Q: Why are some of the fan readings/settings disabled? A: Some monitoring chips do not support 3 fan inputs. Refer to the feature table in techinfo.txt. Also, some chips have 3 fan inputs but the divisor on the 3rd input is fixed at 2. Q: Why is my CPU fan displayed in the wrong place? A: Some motherboard manufacturers (Abit, Intel) have the CPU fan connected to the 3rd fan input. Just change the Fan 3 label to 'CPU'. Q: Why does it show 0RPM even though I have a fan plugged in? A: You need a fan with tachometer output. Such fans usually have 3 wires for +Vcc, ground and tachometer output. If you have such a fan plugged in and it still shows 0RPM you may have to adjust the fan divisor. Q: What are fan divisors for? A: The monitoring chips do not directly return the RPM of the fan directly; instead they return the number of 'counts'. As a guide, use the following divisor values corresponding to your fan's nominal RPM: Divisor Nominal fan RPM 1 8800 2 4400 4 2200 8 1100 In general, if you have a fan connected and the reading shows 0RPM, try selecting a higher divisor. Always use the lowest possible divisor that still gives a non-zero reading to ensure sufficient resolution (jumps between RPM indications). Q: Why don't the fan divisor changes take place immediately? A: Fan divisors have to be set on the hardware monitoring chip and it only takes effect the next time a reading is taken, hence the delay.